home *** CD-ROM | disk | FTP | other *** search
- Path: pangea.Stanford.EDU!karish
- From: karish@pangea.Stanford.EDU (Chuck Karish)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 12 Apr 1996 02:13:10 GMT
- Organization: Mindcraft, Inc.
- Message-ID: <4kke7m$ilr@nntp.Stanford.EDU>
- References: <dewar.828846122@schonberg> <828903511snz@genesis.demon.co.uk> <4kgjrc$4d@news.nyu.edu>
- NNTP-Posting-Host: pangea.stanford.edu
-
- In article <4kgjrc$4d@news.nyu.edu>, halvin <halvin@acf4.nyu.edu> wrote:
- >Lawrence Kirby <fred@genesis.demon.co.uk> writes:
-
- >this might be slightly off-topic, but isn't there a difference between the
- >ANSI and POSIX versions of fprintf? if i remember correctly, the ANSI version
- >returns 0 on success and EOF on failure -- but the POSIX version returns the
- >number of characters printed, or a negative number to indicate failure.
-
- POSIX.1 defers to the C Standard for the specification of fprintf().
- Where POSIX.1 does add requirements on the behavior of C Standard
- features, the intent is always to enforce a more specific requirement
- without violating the C Standard. Any conflict between POSIX.1 and
- Standard C is unintentional and is considered an error to be fixed
- by the POSIX committees.
- --
-
- Chuck Karish karish@mindcraft.com
- (415) 323-9000 x117 karish@pangea.stanford.edu
-